chore(deps-dev): bump jasmine-core from 2.99.1 to 5.1.1 in /build#40956
Conversation
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
|
@dependabot rebase |
1f3e486 to
bb8060e
Compare
bb8060e to
3d42ba7
Compare
|
All the webUI acceptance tests pass, so there is not anything "basic" wrong with the classic web user interface. https://drone.owncloud.com/owncloud/core/39284/7/5 |
|
@DeepDiver1975 this jumps a few major versions. I suppose that there will be a lot of backward-compatibility issues that need fixing. For example: Is someone going to look at this stuff? I am not really a JS guy ;) |
|
A newer version of jasmine-core exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
cf22336 to
cfee958
Compare
|
I manually rebased and force pushed. We can see what fresh CI thinks... |
c1b1f4f to
68df459
Compare
|
https://drone.owncloud.com/owncloud/core/39729/8/5 |
DeepDiver1975
left a comment
There was a problem hiding this comment.
Code Review — Bump jasmine-core from 2.99.1 to 5.1.1 in /build
Automated Dependabot dependency bump for jasmine-core (test framework). Major version bump (2.x → 5.x). This affects the test runner only, not production code.
Run make test-js to verify all existing JS tests still pass with jasmine-core 5.1.1.
Verdict: Needs test validation. Run make test-js to confirm compatibility, then ready to merge.
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Bumps [jasmine-core](https://github.com/jasmine/jasmine) from 2.99.1 to 5.1.1. - [Release notes](https://github.com/jasmine/jasmine/releases) - [Changelog](https://github.com/jasmine/jasmine/blob/main/RELEASE.md) - [Commits](jasmine/jasmine@v2.99.1...v5.1.1) --- updated-dependencies: - dependency-name: jasmine-core dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
68df459 to
ad90322
Compare
DeepDiver1975
left a comment
There was a problem hiding this comment.
Code Review — chore(deps-dev): bump jasmine-core from 2.99.1 to 5.1.1 in /build (updated)
This updated version of the PR now includes JS test fixes alongside the version bump, which materially changes the review:
Test fixes bundled
favoritespluginspec.js: Added OCA.Files.App.initialize() before OC.Plugins.attach(...). This is required in jasmine 5.x because the initialization ordering became stricter. ✅
settingsSpec.js: Removed several empty describe blocks containing only // TODO comments. Jasmine 5.x warns or fails on empty suites. Removing them is correct — empty TODO blocks provide no value and clutter test output. ✅
shareSpec.js: Same — removed one empty describe('Sharing data in table row', ...) TODO block. ✅
Version bump
jasmine-core 2.99.1 → 5.1.1 (lockfile updated). Test infra only, no production code.
The bundled test fixes show this PR has been validated against the new version — the presence of the fixes rather than just a version pin bump is a positive signal.
Verdict: Ready to merge (pending make test-js passing in CI).
Two pre-existing issues exposed by running tests in CI for the first time: 1. jasmine-sinon@0.4.0 calls jasmine.pp() which was removed as a global in jasmine 4+. jasmine-core was bumped to 5.1.1 in #40956 without this being caught. Add a jasmine.pp shim in specHelper.js that redirects to JSON.stringify. 2. setupchecksSpec.js checkDataProtected tests were changed from requests[0].respond() to respondWith+respond() in cf22336 to fix a jasmine 5.x issue, but this breaks with nise 6.1.x (sinon 19+) due to nise behavior changes. The checkWebDAV tests use requests[0].respond() successfully, so revert checkDataProtected to the same direct-respond pattern. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
* ci: add JavaScript unit test job to GitHub Actions Mirror the Drone CI javascript() pipeline in GitHub Actions by adding a local reusable workflow (js-unit.yml) that runs `make test-js` via Karma, and wiring it into ci.yml. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * ci(js-unit): install Firefox from Mozilla PPA instead of snap On ubuntu-latest (24.04), apt-get install firefox installs a snap wrapper. Snap-sandboxed Firefox cannot connect to Karma's loopback socket (localhost:9876), causing all 3 launch attempts to time out. Install the native deb from the Mozilla PPA with a pin rule that ensures it wins over the snap wrapper on any future apt-get run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * fix(js-tests): pin sinon to ^19.0.5 to restore fakeServer in browser sinon v20.0.0 removed nise (the XHR simulation library) from its browser UMD bundle (pkg/sinon.js), causing sinon.fakeServer to be undefined. karma-jasmine-sinon injects pkg/sinon.js and relies on window.sinon.fakeServer, so every test using fakeServer.create() in specHelper.js fails. sinon v19.0.5 is the last version whose browser bundle still exports fakeServer. The broken bump to ^22.0.0 was introduced in commit aaf5f0d (dependabot bump #41548) without test validation. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * fix(js-tests): fix jasmine 5.x incompatibilities in test helpers Two pre-existing issues exposed by running tests in CI for the first time: 1. jasmine-sinon@0.4.0 calls jasmine.pp() which was removed as a global in jasmine 4+. jasmine-core was bumped to 5.1.1 in #40956 without this being caught. Add a jasmine.pp shim in specHelper.js that redirects to JSON.stringify. 2. setupchecksSpec.js checkDataProtected tests were changed from requests[0].respond() to respondWith+respond() in cf22336 to fix a jasmine 5.x issue, but this breaks with nise 6.1.x (sinon 19+) due to nise behavior changes. The checkWebDAV tests use requests[0].respond() successfully, so revert checkDataProtected to the same direct-respond pattern. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * fix(js-tests): restore test isolation broken by Jasmine 5 random ordering Two tests relied on shared mutable state that leaked between specs when Jasmine 5 randomized execution order: - mimeTypeSpec: afterEach restored OC.currentTheme.name but not OC.currentTheme.directory, causing shareSpec's OC.imagePath() calls to return the themed '/themes/abc/...' path instead of the expected default. - setupchecksSpec: oc_dataURL was set once at describe-body level and a test mutated it to false with no cleanup, so subsequent tests saw oc_dataURL===false and checkDataProtected() returned early without making any XHR, leaving suite.server.requests[0] undefined. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * fix(js-tests): fix three more test isolation issues from Jasmine 5 ordering Three more leaks exposed by Jasmine 5's randomised test execution: 1. mimeTypeSpec: afterEach restored OC.currentTheme name/directory but did not flush OC.MimeType._mimeTypeIcons. Tests running after the theme describe got a cache hit with the themed path for 'dir' and failed. 2. l10nSpec: 'calls callback if locale is en' stubbed OC.getLocale but never called localeStub.restore(), leaving getLocale wrapped for any test that ran afterward and tried to stub it again. 3. appSpec (files_sharing): app.js registers a notification handler via $(document).ready at load time. The 'Action events' beforeEach called registerNotificationHandler() a second time without removing the first, so each body event fired two handlers and reload counts were 2 instead of 1. Fix: clear all OCA.Notification.Action handlers before adding the test-owned one. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> * fix(js-tests): restore $.fn.slideUp stub in fileactionsSpec The 'cleans up after hiding' test stubbed $.fn.slideUp globally but never called slideUpStub.restore(). When Jasmine 5 ran this test before any test that relies on slideUp (e.g. coreSpec's menu toggle test), the stub remained active and prevented OC.hideMenus() from hiding elements via slideUp, causing navigation visibility assertions to fail. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> --------- Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Bumps jasmine-core from 2.99.1 to 5.1.1.
Release notes
Sourced from jasmine-core's releases.
... (truncated)
Commits
bff612aBump version to 5.1.14ba42f3Fixed global variable leak when using ParallelReportDispatcher58bee05Documented usage of eval in DelayedFunctionSchedulerc1871b0Removed unnecessary throw when building stack tracec16974bImproved jsdocs for originalFn argument to createSpybfedda9Link to 5.0 upgrade guide in README, not 4.0a67b727Fixed jsdocs for throwUnless and throwUnlessAsync47f3105Bump version to 5.1.0aeb5653Built distribution75d45efExclude inherited Error properties from stack traceMaintainer changes
This version was pushed to npm by sgravrock, a new releaser for jasmine-core since your current version.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)